Skip to content

fix: clarify prereq, installed, post-inst - #480

Open
mikemckiernan wants to merge 2 commits into
NVIDIA:mainfrom
mikemckiernan:mmck-docs-supp-plats
Open

fix: clarify prereq, installed, post-inst#480
mikemckiernan wants to merge 2 commits into
NVIDIA:mainfrom
mikemckiernan:mmck-docs-supp-plats

Conversation

@mikemckiernan

Copy link
Copy Markdown
Member

No description provided.

Signed-off-by: Mike McKiernan <mmckiernan@nvidia.com>
@mikemckiernan mikemckiernan self-assigned this Aug 25, 2026
@github-actions

Copy link
Copy Markdown

Documentation preview

https://nvidia.github.io/cloud-native-docs/review/pr-480

Comment thread confidential-containers/supported-platforms.rst

@mikemckiernan mikemckiernan left a comment

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

More of a question.

- Version
- When It Is Needed
- How It Is Provided
* - `Key Broker Service (KBS) protocol <https://confidentialcontainers.org/docs/attestation/>`__

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fitzthum @fidencio - I think we need a bit of a refinement here. I think the KBS protocol is installed implicitly by shipping the attestation agent, CDH in our guests. So, I think here we want to say that trustee is not installed - and provide a specific trustee version to install, instead.

Then, in above listing for Kata Containers we can say that this comes with a guest using the 0.4.0 KBS protocol. This may make it easier here in turn because we can say to install a trustee version using that same protocol version (or, a protocol version that is compatible, if a patch version increment of the protocol version means that both are still interoperable).

@manuelh-dev

Copy link
Copy Markdown
Contributor

More of a question.

I really like this, thank you for these changes! I left one comment for discussion.

.. flat-table::
:header-rows: 1

* - Interface or Component

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mikemckiernan - if or as we make this change, we could also list genpolicy - we should then merge #479 after this one.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's either merge this one first, then adjust #479, or vice versa.

Signed-off-by: Mike McKiernan <mmckiernan@nvidia.com>
* - NVIDIA B200
- Single-GPU, Multi-GPU

* - NVIDIA HGX B300

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we call out HGX here but not the other rows?
My understanding is that HGX is a platform reference design (inclusive of GPU, switch, CPU) productized by various OEMs. Seems like it should be on all of these rows or none of them. I may certainly be ignorant of other context around HGX though.

* - Artifact
- Release/Version
* - Guest OS
- Distroless

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@manuelh-dev
Is there something more specific we can list here?
I think it's a specific nvidia flavored chiseled os including nvrc.
Is there an upstream kata link to something like a manifest?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants